fix: refresh PASEO_ASSET_HUB genesis after chain reset (0.8.6) - #32
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Paseo Asset Hub was reset. Updated PASEO_ASSET_HUB.genesisHash 0x173cea… → 0xbf0488… to match; verified against the live chain via chain_getBlockHash(0). Bumped to 0.8.6 and updated the integration-test genesis assertion to match.
The stale hash made the host's chain-feature handshake reject product-sdk descriptors regenerated against the new chain - surfacing downstream as the product app stuck disconnected in E2E (paritytech/product-sdk#153)